Provisioning a vehicle experience according to an authentication of a driver for the vehicle experience

ABSTRACT

In some implementations, a vehicle experience system may receive a service request associated with a vehicle. The vehicle experience system may qualify a driver for a vehicle experience involving the vehicle. The vehicle experience system may provide, to a user device associated with the driver, a verification code for authenticating the vehicle experience involving the driver and the vehicle. The vehicle experience system may provide, to a location management system associated with the vehicle, a notification that the vehicle is to be involved in the vehicle experience. The vehicle experience system may provide, to the location management system and based on receiving scan data being associated with the verification code, the authentication of the vehicle experience to enable a provisioning device to facilitate access to the vehicle.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/449,160, filed Sep. 28, 2021, which is incorporated herein byreference in its entirety.

BACKGROUND

A vehicle experience may provide an individual, such as a driver, accessto a vehicle for a period of time to permit the individual to review thevehicle. For example, prior to leasing or purchasing a vehicle, anindividual may have access to the vehicle, via a test drive, to reviewthe vehicle and/or confirm whether the vehicle satisfies theindividual's expectations. Additionally, or alternatively, a vehicleexperience may involve a driver gaining rental access to a vehicleand/or recreational access to a vehicle for a limited period of time.

SUMMARY

In some implementations, a system for authenticating a driver for avehicle experience includes one or more memories and one or moreprocessors, communicatively coupled to the one or more memories,configured to: receive, from a user device, a service request associatedwith the driver and a vehicle, wherein the service request includesdriver information associated with the driver and vehicle informationassociated with the vehicle; obtain, based on the driver information,qualification information associated with the driver; provide, to theuser device and based on the qualification information indicating thatthe driver is qualified for the vehicle experience, a verification codethat is associated with the driver and the vehicle; identify, based onthe vehicle information, a location management system that is associatedwith the vehicle; and cause the location management system to provisionthe vehicle experience based on the verification code; receive, from thelocation management system, an authentication request associated with ascan of the verification code; authenticate the driver for the vehicleexperience based on the authentication request including scan dataassociated with the verification code; and cause, based onauthenticating the driver for the vehicle experience, the locationmanagement system to enable the driver to access the vehicle.

In some implementations, a non-transitory computer-readable mediumstoring a set of instructions includes one or more instructions that,when executed by one or more processors of a device, cause the deviceto: receive a service request associated with a vehicle, wherein theservice request includes driver information associated with a driver andvehicle information associated with the vehicle; qualify, based on thedriver information, the driver for a vehicle experience involving thevehicle; provide, to a user device associated with the driver and basedon qualifying the driver for the vehicle experience, a verification codefor authenticating the vehicle experience involving the driver and thevehicle; provide, to a location management system associated with thevehicle, a notification that the vehicle is to be involved in thevehicle experience, wherein the notification is configured to cause thelocation management system to provision the vehicle experience based onan authentication of the driver; receive, from the location managementsystem, scan data associated with a scan of the verification code by aprovisioning device associated with the location management system; andprovide, to the location management system and based on the scan databeing associated with the verification code, the authentication of thevehicle experience to enable the provisioning device to facilitateaccess to the vehicle.

In some implementations, a method for authenticating a driver for avehicle experience includes receiving, from a user device, a servicerequest for a vehicle experience; qualifying, based on driverinformation in the service request, the driver for the vehicleexperience; identifying, based on qualifying the driver, a vehicle forthe vehicle experience that is associated with vehicle information inthe service request; generating, based on vehicle experience informationin the service request, a digital vehicle key that facilitates access tothe vehicle for the vehicle experience; and providing, to the userdevice, the digital vehicle key to permit the driver to access to thevehicle via the user device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1D are diagrams of an example implementation relating toprovisioning a vehicle experience according to an authentication of adriver for the vehicle experience.

FIGS. 2A and 2B are diagrams of an example implementation describedherein.

FIG. 3 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 4 is a diagram of example components of one or more devices of FIG.3 .

FIG. 5 is a flowchart of an example process relating to provisioning avehicle experience according to an authentication of a driver for thevehicle experience.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A test drive typically involves an individual requesting a seller (e.g.,an individual or organization, such as a manufacturer, dealer, or otherentity that sells vehicles) to allow the individual to drive a vehiclefor a period of time and accessing the vehicle from a location of theseller. For example, a consumer may arrive at a dealership and requestthe dealership to authorize the test drive. An agent (or representative)of the dealership, via an in-person interaction with the consumer, maydetermine whether to authorize the test drive based on whether theconsumer is qualified to the drive the vehicle (e.g., based on whetherthe agent verifies that the consumer has a driver license to drive atype of the vehicle and/or insurance coverage to drive the vehicle).Accordingly, via such a review, the agent and/or the dealership mayattempt to maintain security of the vehicle by authenticating theconsumer (e.g., using the consumer's driver license as anidentification) and/or qualifying the consumer as a driver for thevehicle experience. However, because malicious individuals canrelatively easily falsify an identification, such an authenticationprocess can be unreliable. Accordingly, certain systems may be incapableof enabling a dealership to accurately authenticate or qualify a driverfor a vehicle experience and/or may prevent the dealership fromprovisioning a vehicle experience without an agent reviewing theconsumer's qualification information.

Furthermore, in some cases, the consumer may need to provide personalinformation, such as contact information (e.g., a name, residentialaddress, telephone number, and/or email address), that would permit theagent (e.g., a sales associate or marketing representative) or thedealership to further communicate with the consumer, regardless of theconsumer's desire to continue to communicate with the dealership orcontinue a relationship with the dealership following the vehicleexperience. In such a case, certain systems may be incapable of enablingthe consumer to engage in a vehicle experience without providing certainpersonal information to the dealership, thereby preventing the consumerfrom engaging in the vehicle experience while remaining anonymous.

Some implementations described herein provide a vehicle experiencesystem that enables a consumer (e.g., a driver) to engage in a vehicleexperience involving a vehicle without the consumer having to engage inan in-person interaction at the dealership and/or provide personalinformation associated with the consumer. For example, the vehicleexperience system may receive a service request for a vehicle experienceinvolving a vehicle, identify a system associated with the vehicle(e.g., a location management system that manages an inventory of adealership associated with the vehicle), and automatically authenticatea driver for the vehicle experience and/or provision the vehicleexperience. More specifically, the vehicle experience system and/or thesystem may automatically (e.g., based on an authentication of thedriver) provide a key to the vehicle (e.g., a physical vehicle keyand/or a digital key) to provision the vehicle experience. In someimplementations, the vehicle experience system may authenticate thevehicle experience and/or the driver via a verification code that can begenerated based on specific information associated with the driverand/or the requested vehicle experience. As described herein, theverification code may provide enhanced security over anidentification-based authentication that is performed during anin-person interaction (e.g., by allowing for a multi-factorauthentication using a user device and/or application on the userdevice) while enabling the driver to remain anonymous. In someimplementations, the vehicle experience system may be configured toqualify the driver for the vehicle experience system based onqualification information (e.g., driver license information, vehicleinsurance information, background information, financial information,and/or another type of qualification information) associated with thedriver. The driver may be a consumer seeking to purchase or lease thevehicle and/or a user of the vehicle experience system that does not ownthe vehicle at the time of the vehicle experience.

In this way, the vehicle experience system may securely facilitateand/or provision a vehicle experience at a dealership location or otherlocation associated with a vehicle involved in the vehicle experience.Accordingly, the vehicle experience system may prevent fraud, provideflexibility and efficient scheduling or provisioning of vehicleexperiences for consumers and/or dealerships, and enhance a consumerexperience involved in test driving a vehicle or engaging in other typesof vehicle experiences, such as viewing a vehicle and/or testingfeatures of the vehicle without test driving the vehicle, among otherexamples.

FIGS. 1A-1D are diagrams of an example implementation 100 relating toprovisioning a vehicle experience according to an authentication of adriver for the vehicle experience. As shown in FIGS. 1A-1D, exampleimplementation 100 includes a vehicle experience system, a user deviceassociated with a user (User A), one or more location management systems(Location Management System 1, Location Management System 2, and so on)associated with corresponding vehicle locations (Location 1, Location 2,and so on), a provisioning device, a driver qualification source, and anagent device associated with an agent (Agent B). In exampleimplementation 100, a set of N vehicles (Vehicle 1-1 to Vehicle 1-N) areassociated with a first location management system (Location 1) andanother set of M vehicles (Vehicle 2-1 to Vehicle 2-M) are associatedwith a second location management system (Location 2). These systemsand/or devices are described in more detail below in connection withFIG. 3 and FIG. 4 .

In example implementation 100, the user may be qualified as a driver fora test drive involving a vehicle and the test drive may be automaticallyprovisioned for the user without an in-person interaction with the agentand/or without the user having to provide personal information (e.g.,contact information) to the agent (thereby enabling the user to remainanonymous during the test drive). The agent may be a representative(e.g., a sales representative and/or a customer service representative)of an entity (e.g., a dealership) that owns and/or operates a vehiclelocation (e.g., Location 1) and/or a vehicle (e.g., Vehicle 1-1).Accordingly, in some implementations, the agent may be authorized, viathe agent device and/or by the entity, to provision a vehicle for thetest drive. Although example implementation 100 is described inconnection with a vehicle experience that involves a test drive of avehicle, example implementation 100 may include or involve other typesof vehicle experiences.

As shown in FIG. 1A, and by reference number 105, the user initiates arequest for a vehicle experience. For example, the user may initiate aservice request via the user device and/or an application of the userdevice. The application may be associated with the vehicle experiencesystem and/or be configured to permit a user of the application (and/orthe user device) to be authenticated as a driver for a vehicleexperience involving a vehicle. In some implementations, the user mayhave an account associated with the application and/or be required tolog into the application via a user credential (e.g., a username, anaccount identifier, a password, and/or a biometric scan, among otherexamples), which may serve as a factor (e.g., a first factor) of amulti-factor authentication described herein.

In some implementations, the application may have access to the locationmanagement systems. Accordingly, the application may permit the user toidentify or browse an inventory of N vehicles associated with the firstlocation management system and/or an inventory of M vehicles associatedwith the second location management system, and so on. Additionally, oralternatively, one or more of the location management systems may beaccessible through a website (e.g., a dealership website associated withthe vehicle locations). In this way, the user may initiate a request fora vehicle experience by browsing a vehicle inventory associated with alocation management system and/or selecting or indicating a vehicleexperience involving a vehicle (e.g., selecting the vehicle for a testdrive and/or indicating that the user is interested in test driving thevehicle). Based on a selection of the vehicle (e.g., Vehicle 1-1) and/orthe location management system, the user device (and/or the application)may receive, from the user, vehicle information for a vehicle of avehicle experience.

The user, when initiating the service request, may provide, to the userdevice and/or the application, driver information associated with theuser that may be used to set up a vehicle experience, authenticateand/or qualify the user for the vehicle experience, and/or provision thevehicle experience, as described herein. Additionally, or alternatively,the user may provide the driver information when setting up an accountassociated with the application.

As further shown in FIG. 1A, and by reference number 110, the userdevice transmits the service request to the vehicle experience system.The user device may transmit the service request based on a user inputfrom the user. The user input may cause transmission of the servicerequest. In this way, the user may provide the service request to causethe vehicle experience system and/or the location management system toset up or provision a vehicle experience involving a selected vehicle(e.g., a particular vehicle from a particular vehicle inventoryassociated with a particular vehicle location) and/or a vehicle thatmeets certain criteria that are indicated in the vehicle informationprovided by the user to the user device. As described herein, theservice request may include vehicle information associated with avehicle and/or driver information associated with the user.

The vehicle information may identify a vehicle characteristic associatedwith the vehicle. For example, the vehicle information may identify amake and/or a model of a vehicle (Vehicle 1 in example implementation100), a year of manufacture of the vehicle, a vehicle identificationnumber (VIN) of the vehicle, a trim level of the vehicle (or specificfeatures of the vehicle), a type of the vehicle, a location of thevehicle (which may correspond to a location of the vehicle location oran entity that owns or is managing a sale or lease of the vehicle),and/or an identifier of an entity associated with the locationmanagement systems. In this way, the user device and/or the applicationmay receive vehicle information associated with a vehicle that may beinvolved in a vehicle experience with the user, as described herein.

The driver information may identify a driver characteristic of the userthat may be used to authenticate the user and/or verify that the usermay be a qualified driver of the vehicle. For example, the driverinformation may indicate a name of the user, an age of the user, vehiclepreferences of the user (e.g., one or more characteristics of thevehicle that are preferred by the user), and/or other user profileinformation associated with a vehicle or vehicle experience. In someimplementations, the driver information may identify a location of theuser (e.g., a current location of the user device and/or a location of aresidence of the user). In some implementations, the location of theuser may correspond to a desired location for a vehicle experienceinvolving the vehicle (e.g., a location of the user and/or a locationassociated with the location management system that is nearest theuser). In this way, the user device and/or the vehicle experience systemmay receive driver information and/or vehicle information for thevehicle experience to permit the user to be qualified as a driver and/orto permit a location management system to provision a vehicle for thevehicle experience, as described herein.

In some implementations, the driver information (and/or the servicerequest) may include qualification information that is associated withthe user being a qualified driver. For example, the qualificationinformation may include driver license information associated with theuser's driver license. The driver license information may include a nameof the user on the driver license, an address associated with the useron the driver license, a date of issuance, an expiration date, a uniqueidentification number, a jurisdiction that issued the driver license,and/or a class of vehicles that the user is qualified to drive (e.g., acommercial driver license class or non-commercial driver license class),among other examples. In some implementations, the qualificationinformation may include an image of the driver license (e.g., an imagecaptured by a camera of the user device that depicts the driver licenseof the user).

The qualification information may include insurance informationassociated with the user. The insurance information may identify apolicy associated with the user operating a vehicle, a policy associatedwith the user operating a particular class of vehicle, an insuranceagency that issued the policy, an issue date or expiration date of thepolicy, or other insurance information. In this way, the user deviceand/or the vehicle experience system may receive qualificationinformation associated with the user to permit the user to be qualifiedfor a vehicle experience (e.g., to be qualified to test drive thevehicle).

As further shown in FIG. 1A, and by reference number 115, the vehicleexperience system obtains a qualification from the driver qualificationsource. For example, the vehicle experience system may obtain thequalification based on the driver information and/or the vehicleinformation. More specifically, the vehicle experience system may obtainthe qualification using qualification information.

The driver qualification source may be a system that is configured tovalidate qualification information associated with a user to qualify theuser as a driver for the vehicle experience. For example, the driverqualification source may be associated with a driver database of ajurisdiction that issued the user's driver license. In such a case, thevehicle experience system may obtain, from the driver qualificationsource, a qualification that indicates that the user is a licenseddriver (e.g., based on the driver qualification source validating thedriver license information and/or an image of the user's driverlicense). Additionally, or alternatively, the driver qualificationsource may be associated with an insurance policy database of aninsurance agency that issued an indicated insurance policy in thequalification information. In such a case, the vehicle experience systemmay obtain, from the driver qualification source, a qualification thatindicates that the user is insured to drive the vehicle (e.g., based onthe driver qualification source validating that the insurance policycovers the user, a class of the vehicle, and/or the requested vehicleexperience).

In some implementations, a driver qualification source may be configuredto prequalify the user for a loan from a financial institution relatedto purchasing the vehicle requested for the service request and/or avehicle involved in the vehicle experience. The user may interact withthe user device to select an option associated with becomingpre-qualified for the loan. For example, the user device may enable theuser to input information associated with becoming pre-qualified for theloan. More specifically, a user interface of the user device may displayone or more text input fields through which the user can inputinformation requested by a financial institution (which may beassociated with a driver qualification source and/or be one of thedriver prequalification sources) to pre-qualify the user for a loan. Theuser may input the requested information and the user device (e.g., theserver device associated with the user interface) may provide the inputinformation to the financial institution. Correspondingly, the vehicleexperience system may qualify the user as a driver for the vehicleexperience if the driver qualification source (and/or the financialinstitution) indicates that the driver is prequalified for a loan topurchase the vehicle.

In this way, the vehicle experience system may obtain one or morequalifications for the user to engage in the vehicle experience systemfrom one or more corresponding driver qualification sources thatprocessed the qualification information. Correspondingly, the vehicleexperience system may qualify the user as a driver for the vehicleexperience. Therefore, the vehicle experience system may permit the userto be qualified for a vehicle experience without the user having toprovide physical documentation and/or identification to an individual(e.g., the agent) at a vehicle location associated with the vehicle.

As further shown in FIG. 1A, and by reference number 120, the vehicleexperience system generates a verification code. The vehicle experiencesystem may generate the verification code for use in authenticating thedriver and/or provisioning the vehicle experience, as describedelsewhere herein. The vehicle experience system may generate theverification code based on qualifying the driver for the vehicleexperience.

The verification code may include an optical code that is configured tobe scanned from an output component of the user device via a scanner(e.g., an image capture device, such as a camera) of the provisioningdevice. In some implementations, the agent device may be used to scanthe verification code to authenticate the user without the user havingto provide personal information to the agent and/or without the agenthaving to authenticate the user using a physical identification (e.g., adriver license of the user). For example, the verification code mayinclude a one-dimensional barcode (e.g., a parallel line code), atwo-dimensional barcode (e.g., quick response (QR) code), and/or ananimated or dynamic code. Accordingly, the verification code may be usedto verify, once the verification code is scanned by the agent device,that the user and the agent are engaging in a vehicle experience, asdescribed elsewhere herein.

The vehicle experience system may generate the verification code using acode generator. The code generator may be associated with theapplication and/or utilize any suitable encryption technique to generatethe verification code. The code generator may be associated with and/orinstalled on the vehicle experience system or another system.Additionally, or alternatively, the code generator may be locallyinstalled on the user device.

In some implementations, the verification code may be generated based onthe driver information associated with the user and/or vehicleinformation associated with the vehicle. For example, the vehicleexperience system may generate the verification code based on a drivercharacteristic of the user and/or a vehicle characteristic of thevehicle. In some implementations, the vehicle experience system maygenerate the verification code based on qualification informationassociated with qualifying the user as a driver for the vehicleexperience. Additionally, or alternatively, the vehicle experiencesystem may generate the verification code based on a vehiclecharacteristic of the vehicle that is identified in the vehicleinformation. The vehicle experience system may generate the verificationcode based on a device characteristic associated with the user device(e.g., a device identifier of the user device, account informationassociated with an account of the application, a location of the userdevice) and/or a request characteristic associated with the servicerequest (e.g., a time associated with the user requesting the vehicleexperience, an agent or vehicle location identified in the servicerequest, and/or the like).

Accordingly, the verification code may be generated as a unique codethat is configured specifically for a vehicle experience involving theuser and/or the vehicle. More specifically, the verification code may begenerated based on an encryption of the driver information or thevehicle information to enable the driver to automatically beauthenticated for a specific vehicle experience and/or to enable thespecific vehicle experience to automatically be provisioned.Accordingly, the user and/or the vehicle experience may be securelyauthenticated and/or provisioned without the user having to interactwith the agent and/or without the user having to provide confidentialinformation to the agent or the entity associated with the vehicle.

As shown in FIG. 1B, and by reference number 125, the vehicle experiencesystem provides the verification code to the user device. The vehicleexperience system may provide the verification code based on receivingthe qualification of the driver from a driver qualification source thatprocessed the qualification information of the user. In this way, theuser device may receive the verification code to permit the user to beauthenticated as a driver for a vehicle experience and/or to permit thevehicle experience to automatically be provisioned, as describedelsewhere herein.

As further shown in FIG. 1B, and by reference number 130, the vehicleexperience system and/or a location management system (LocationManagement System 1) schedules the vehicle experience involving thevehicle. For example, the vehicle experience system may interact withthe location management system to schedule the vehicle experience duringa requested time frame of the user (e.g., as indicated in the servicerequest) and/or an available time frame for the vehicle experience asindicated by the location management system. The location managementsystem may indicate an available time frame for the vehicle experiencebased on accessing a calendar associated with the vehicle (e.g., acalendar that indicates time frames that the vehicle is available forthe vehicle experience) and/or an entity associated with the locationmanagement system. In this way, the vehicle experience system and/or thelocation management system may coordinate to schedule the vehicleexperience during a time period that overlaps a time frame requested bythe user and an available time frame for the vehicle experience asindicated by the location management system.

The vehicle experience system may identify the location managementsystem using a vehicle inventory data structure (e.g., a data structurethat maps a vehicle and/or characteristics of a vehicle to acorresponding location of the vehicle). Accordingly, the vehicleexperience system may identify the location management system as beingassociated with the vehicle and/or the user based on information fromthe service request. For example, the vehicle experience system maydetermine that the location management system is associated with thevehicle, based on the vehicle information identifying a VIN of thevehicle and an inventory mapping (e.g., within the vehicle inventorydata structure) that indicates that the location management system isassociated with the vehicle. Additionally, or alternatively, the vehicleexperience system may identify the location management system based ondetermining, from the inventory mapping, that the location managementsystem is associated with one or more vehicles that satisfy certaincriteria of a vehicle identified in the service request. In someimplementations, the vehicle experience system may select the locationmanagement system, from the plurality of location management systems, toreceive provisioning information and/or facilitate a vehicle experiencebased on the location management system being associated with a vehiclelocation that is within a certain distance of a location of the user(and/or the user device).

As further shown in FIG. 1B, and by reference number 135, the vehicleexperience system provides provisioning information to the locationmanagement system. For example, the vehicle experience system mayprovide the provisioning information within a notification that the userrequested the vehicle experience involving a vehicle associated with thelocation management system. The vehicle experience system may providethe notification based on the vehicle information indicating that thevehicle is associated with the location management system.

The vehicle experience information may include information associatedwith the driver and/or the vehicle to the location management systemand/or the provisioning device to authenticate the user and/or provisionthe vehicle experience, as described elsewhere herein. For example, thevehicle provisioning information may include a qualification of thedriver and/or information associated with the verification code topermit the provisioning device to authenticate the driver via theverification code and/or provision the vehicle experience based on ascan of the verification code. Additionally, or alternatively, thevehicle experience information may include a VIN of the vehicle and/orrequested criteria for a vehicle for the vehicle experience. In thisway, the location management system and/or the provisioning device mayidentify the vehicle (e.g., based on a mapping of the vehicle to a keyregistry of the location management system and/or the provisioningdevice) and/or find a vehicle that meets certain criteria of a vehiclerequested by the user in the service request.

As shown in FIG. 1C, and by reference number 140, the user devicefacilitates a scan of the verification code to provision the vehicleexperience. For example, the user device may display the verificationcode via a display device of the user device. In this way, because theverification code is to be displayed within a field of view of a scannerof the provisioning device, a scan of the verification code mayrepresent an authentication of the user and/or a vehicle experienceinvolving the user as a qualified driver of the vehicle for the vehicleexperience.

While certain examples are described herein in connection with averification code being displayed as an optical code, other types ofverification codes may be considered to authenticate a driver for avehicle experience. For example, an audible code may be emitted from aspeaker of the user device so that the provisioning device can interpretan audio signal from the speaker that includes the audible code.Additionally, or alternatively, the code may be emitted and/orcommunicated via a wireless communication signal (e.g., a BLUETOOTH®signal, a BLUETOOTH LOW-ENERGY® (BLE) signal, a near field communication(NFC) signal, or other type of wireless communication protocol signal).

As further shown in FIG. 1C, and by reference number 145, theprovisioning device and/or the agent device scans the verification code.For example, the user may cause a scanner of the provisioning device toscan and/or decode the verification code. Additionally, oralternatively, the agent may cause a scanner of the agent device to scanand/or decode the verification code. A scanner (e.g., of theprovisioning device and/or the agent device) may include a barcodescanner and/or an image capture device.

In some implementations, the provisioning device may decode theverification code by processing scan data from the scanner. For example,the provisioning device may decode the verification code in associationwith a decryption technique (e.g., a decryption technique provided inthe provisioning information and/or that is configured for use withinthe provisioning device) that corresponds to the encryption techniqueused by the code generator to generate the verification code. In thisway, the provisioning device may obtain driver information (e.g., driverlicense information, an image of the user's driver license,qualification information, or a qualification of the user as a driverfor the vehicle experience system) associated with the user to permitthe provisioning device, the location management system and/or thevehicle experience to authenticate the user as a driver for the vehicleexperience. For example, the provisioning device may prompt the user toprovide another factor for authentication of the user (e.g., a factorthat is decoded from the decrypting of the verification code). In thisway, in combination with the user providing a credential associated withthe application as described above, the provisioning device mayfacilitate multi-factor authentication of the user to authenticate thedriver for the vehicle experience, thereby providing improved securityover other systems or authentication techniques (e.g., using only aphysical identification of the user).

Similarly, the agent device (e.g., in the event that the provisioningdevice is inoperable or inaccessible) may scan the verification code toauthenticate the user as a driver and/or provision the vehicleexperience. The agent, based on the agent device obtaining vehicleinformation associated with the vehicle from decoding the verificationcode, may request the user to verify a characteristic of the vehicle,thereby obtaining another factor for authenticating the user as a driverfor the vehicle experience. In such a case, the agent may securely(e.g., via a multi-factor authentication process and without reviewing aphysical identification of the user) provision the vehicle experiencewithout obtaining personal information associated with the user (e.g.,by providing a physical vehicle key to the vehicle), thereby permittingthe user to be anonymously authenticated as a driver for the vehicleexperience.

As further shown in FIG. 1C, and by reference number 150, the vehicleexperience system and/or the location management system may authenticatethe vehicle experience. In some implementations, the provisioning deviceand/or the agent device may provide an authentication request to thelocation management system and/or the vehicle experience system inassociation with the scan of the verification code. Accordingly, thevehicle experience system may receive the authentication request topermit the vehicle experience system to decrypt the scan data accordingto a decryption technique that corresponds to the encryption technique.In such a case, based on the scan data being associated with a scan ofthe verification code for the vehicle experience, the vehicle experiencesystem may provide driver information and/or vehicle information to theprovisioning device to facilitate authentication of the user as a driverfor the vehicle experience and/or indicate the vehicle (Vehicle 1-1)that is involved in the vehicle experience.

As further shown in FIG. 1C, and by reference number 155, theprovisioning device and/or the agent may provision the vehicleexperience. For example, based on authenticating the user and/or thevehicle experience, the vehicle experience system (and/or locationmanagement system) may cause the provisioning device to enable access tothe vehicle and/or instruct the agent (e.g., via the agent device) topermit the user to access the vehicle.

The provisioning device may be configured to enable access to a physicalvehicle key of the requested vehicle (e.g., similar to a vendingmachine). In this way, the user may obtain automatic access to thevehicle for the vehicle experience without having to interact with theagent or the entity associated with the vehicle. Moreover, the user maybe authenticated as a driver for the vehicle experience without being anowner of the vehicle (e.g., because the user is indicated as qualifiedto drive the vehicle according to a qualification from the driverqualification source and/or authenticated as the driver according to themulti-factor authentication process described herein).

As shown in FIG. 1D, and by reference number 160, the vehicle experiencesystem may monitor the vehicle experience. For example, to maintainsecurity of the vehicle (e.g., for the entity), the vehicle experiencesystem may be configured to receive location information associated withthe user device (e.g., via the application) and/or timing informationassociated with the vehicle experience (e.g., to ensure that a timeperiod associated with the vehicle experience does not expire prior tothe user returning the vehicle to the vehicle location). In someimplementations, based on the vehicle experience traveling outside of aparticular distance from the vehicle location (e.g., using a geofence orthe like), the vehicle experience system may send a notification to theagent device or other system to alert the agent (or other authorities)of potential fraudulent activity involving the vehicle (which mayinvolve a theft of the vehicle). Additionally, or alternatively, thevehicle experience system may similarly provide a notification if thevehicle, during the vehicle experience system, appears to be driven froma different course provided, via the application to the user during thevehicle experience. In some implementations, in the event that the user,via the user device, stops sharing location information associated withthe user device, the vehicle experience system may similarly send anotification to the agent to indicate the potential fraudulent activity.

Additionally, or alternatively, if the user follows certain instructions(e.g., navigation instructions, timing instructions associated with aduration of the vehicle experience, or the like), the vehicle experiencemay maintain that information in association with the account of theuser (e.g., to offer an award or discount associated with purchasing thevehicle and/or to track a trust level associated with the user engagingin a vehicle experience that involves automatic or anonymousprovisioning, as described herein).

As further shown in FIG. 1D, and by reference number 165, the vehicleexperience system manages information associated with the vehicleexperience. In some implementations, the vehicle experience system maymonitor information from the user device, the agent device, and/or thevehicle to manage, via a record log, the vehicle experience. The recordlog may be associated with the user and/or the vehicle (e.g., tomaintain a database of vehicles that the user test drove, a trust levelof the user, and/or to maintain a database of test drivers of thevehicle). Accordingly, the vehicle experience system may manage theinformation associated with the vehicle experience by storing, in arecord log, the driver information and/or the vehicle information inassociation with the vehicle experience (e.g., using an entry or recordthat is identified by an identifier associated with the vehicleexperience).

In some implementations, the vehicle experience system may verify whichvehicle is involved in the vehicle experience. For example, the vehicleexperience system may request and/or receive an identifier (e.g., a VIN)of the vehicle from the provisioning device (which may have identifiedthe vehicle based on the VIN being mapped to the provided physicalvehicle key). Accordingly, the vehicle experience system may store theidentifier of the vehicle in association with the driver information toconfirm that the user and the vehicle were involved in the vehicleexperience. Additionally, or alternatively, the vehicle experiencesystem may provide a notification to the user device that verifies thatthe vehicle is the vehicle that was requested by the user and/or thatthe vehicle satisfies certain criteria requested by the user via theservice request.

In some implementations, the vehicle experience system may requestand/or receive feedback from the user via the user device. The feedbackmay be associated with the vehicle experience and indicate whether theuser test drove the vehicle, whether the vehicle matched the requestedvehicle and/or certain criteria indicated in the service request,whether the user was satisfied with certain features of the vehicle or aperformance of the vehicle during the vehicle experience, and/or asentiment of the user relative to the vehicle experience.

Accordingly, as described herein, the vehicle experience system mayenable a user (or driver) to be qualified to engage in a vehicleexperience, be authenticated as a driver for the vehicle experience, andanonymously access a vehicle for the vehicle experience whilemaintaining safety and security of an agent involved in the vehicleexperience and/or the vehicle. Furthermore, the vehicle experiencesystem may automatically provision a vehicle for a vehicle system byproviding a vehicle key (e.g., a physical vehicle key) to the userwithout the user having to interact with an agent of the entity.Accordingly, the vehicle experience system may provide, over othersystems, a more convenient vehicle experience for a user, withoutsacrificing the safety or security of the vehicle. Furthermore, thevehicle experience system may allow for improved efficiency with respectto offering certain vehicle experiences by enabling a user to beaccurately qualified as a driver without requiring an in-personinteraction between the user and a seller of a vehicle.

As indicated above, FIGS. 1A-1D are provided as an example. Otherexamples may differ from what is described with regard to FIGS. 1A-1D.The number and arrangement of devices shown in FIGS. 1A-1D are providedas an example. In practice, there may be additional devices, fewerdevices, different devices, or differently arranged devices than thoseshown in FIGS. 1A-1D. Furthermore, two or more devices shown in FIGS.1A-1D may be implemented within a single device, or a single deviceshown in FIGS. 1A-1D may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) shown in FIGS. 1A-1D may perform one or more functionsdescribed as being performed by another set of devices shown in FIGS.1A-1D.

FIGS. 2A-2B are diagrams of an example implementation 200 associatedwith provisioning a vehicle experience according to an authentication ofa driver for the vehicle experience. As shown in FIGS. 2A-2B, exampleimplementation 200 includes a vehicle experience system, a user deviceassociated with a user (User A), and a location management system(Location Management System 1) associated with a vehicle location(Location 1). One or more examples of example implementation 200 maycorrespond to similar examples of example implementation 100 (e.g., asexamples that may correspondingly be performed as alternatives or inaddition to corresponding examples of example implementation 100). Thesedevices are described in more detail below in connection with FIG. 3 andFIG. 4 .

As shown in FIG. 2A, and by reference number 225, the vehicle experiencesystem generates and/or provides a digital vehicle key to the userdevice. For example, the vehicle experience system may generate and/orprovide the digital vehicle key in a similar manner as described abovein connection with the verification code of example implementation 100.More specifically, the vehicle experience system may generate and/orprovide the digital vehicle key based on receiving a service request fora vehicle experience and/or based on qualifying the user for the vehicleexperience, as described elsewhere herein.

In example implementation 200, the digital vehicle key may correspond toa wireless key (a passcode that can be transmitted to the vehicle viaany suitable technique, such as BLUETOOTH®, near field communication(NFC), Wi-Fi, or the like) that provides access to the vehicle.Accordingly, using any suitable encryption technique, the vehicleexperience system may generate the digital vehicle key to be configuredto wirelessly enable access to the vehicle via the user device (e.g.,using the application of the user device).

In some implementations, the digital vehicle key may be configured toenable access to the vehicle (or allow the vehicle to operate) for aparticular time period. For example, based on a time period associatedwith the vehicle experience (e.g., a time requested in the servicerequest and/or scheduled as described herein), the vehicle experiencesystem may configure the digital vehicle key to enable access to thevehicle only during the time period. In the event that the vehicleexperience is initiated before the time period, the digital vehicle keymay not allow access to the vehicle. Additionally, or alternatively, ifthe vehicle experience extends beyond an expiration of the time period,the digital vehicle key may expire and be configured to instruct orcause the vehicle to shut down (e.g., perform one or more operations tosafely slow the vehicle and/or prevent a current driver from driving thevehicle). In this way, the vehicle experience system may configure thedigital vehicle key to allow access to or operation of the vehicle onlyduring a time period that is associated with the vehicle experience,thereby providing security over a vehicle experience that may beautomatically provisioned using the digital vehicle key, as describedherein.

Additionally, or alternatively, the digital vehicle key may beconfigured to enable access to the vehicle (or allow the vehicle tooperate) within a particular area. For example, based on a location ofthe vehicle (e.g., the vehicle location) and/or the vehicle experience(e.g., a location requested in the service request or identified basedon the vehicle information as described herein), the vehicle experiencesystem may configure the digital vehicle key to enable access to thevehicle only within an area (e.g., which may be defined by a certaindistance from the location) of the vehicle location.

As further shown in FIG. 2A, and by reference number 235, the vehicleexperience system may provide provisioning information to the locationmanagement system. For example, the vehicle experience system mayprovide the provisioning information in a similar manner as describedabove in connection with example implementation 100. In someimplementations, the provisioning information may include a notificationto provision the vehicle for the vehicle experience during a time periodidentified in the vehicle experience system. In such a case, the digitalvehicle key may be generated based on a confirmation that the locationmanagement system has provisioned the vehicle (e.g., scheduled orallocated the vehicle for the vehicle experience) for the vehicleexperience system. For example, the digital vehicle key may be generatedto enable access to the vehicle only the time period that is confirmedby the location management system (e.g., via a scheduling technique orprotocol, as described herein).

As shown in FIG. 2B, and by reference number 260, the vehicle experiencesystem and/or the location management system provisions the vehicle forthe vehicle experience. For example, the vehicle experience system mayprovide information associated with the digital vehicle key that permitsthe vehicle to recognize the user device based on the user deviceproviding (or broadcasting) the digital vehicle key (e.g., via awireless communication).

As further shown in FIG. 2B, and by reference number 270, the userdevice utilizes the digital vehicle key for the vehicle experience. Forexample, when the user is within a wireless communication range of thevehicle and/or a certain distance of the vehicle (e.g., a distance thatmay be defined by a wireless communication protocol used to broadcastthe digital vehicle key), the digital vehicle key and/or user device maypermit the user to unlock, access, activate, and/or drive the vehicleduring the vehicle experience. In this way, as described herein, thevehicle experience may automatically be provisioned in a manner thatpermits the user to access the vehicle using a digital vehicle key.Accordingly, in such an example, the user may not have to access aprovisioning device or interact with an agent to obtain a physical key,which may be required for vehicles that are not compatible or incapableof operating using a digital vehicle key.

As indicated above, FIGS. 2A-2B are provided as an example. Otherexamples may differ from what is described with regard to FIGS. 2A-2B.The number and arrangement of devices shown in FIGS. 2A-2B are providedas an example. In practice, there may be additional devices, fewerdevices, different devices, or differently arranged devices than thoseshown in FIGS. 2A-2B. Furthermore, two or more devices shown in FIGS.2A-2B may be implemented within a single device, or a single deviceshown in FIGS. 2A-2B may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) shown in FIGS. 2A-2B may perform one or more functionsdescribed as being performed by another set of devices shown in FIGS.2A-2B.

FIG. 3 is a diagram of an example environment 300 in which systemsand/or methods described herein may be implemented. As shown in FIG. 3 ,environment 300 may include a vehicle experience system 310, a userdevice 320, an agent device 330, a location management system 340, aprovisioning device 350, a vehicle 360, driver qualification source 370,and a network 380. Devices of environment 300 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

The vehicle experience system 310 includes one or more devices capableof receiving, generating, storing, processing, providing, and/or routinginformation associated with authenticating a vehicle experience and/orprovisioning the vehicle experience, as described elsewhere herein. Thevehicle experience system 310 may include a communication device and/ora computing device. For example, the vehicle experience system 310 mayinclude a server, such as an application server, a client server, a webserver, a database server, a host server, a proxy server, a virtualserver (e.g., executing on computing hardware), or a server in a cloudcomputing system. In some implementations, the vehicle experience system310 includes computing hardware used in a cloud computing environment.

The user device 320 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith a driver requesting and/or facilitating provisioning of a vehicleexperience, as described elsewhere herein. The user device 320 mayinclude a communication device and/or a computing device. For example,the user device 320 may include a wireless communication device, amobile phone, a user equipment, a laptop computer, a tablet computer, adesktop computer, a set-top box, a wearable communication device (e.g.,a smart wristwatch, a pair of smart eyeglasses, a head mounted display,or a virtual reality headset), or a similar type of device.

The agent device 330 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith facilitating an authentication of a driver for a vehicleexperience, as described elsewhere herein. The agent device 330 mayinclude a communication device and/or a computing device. For example,the agent device 330 may include a wireless communication device, amobile phone, a user equipment, a laptop computer, a tablet computer, adesktop computer, a wearable communication device (e.g., a smartwristwatch, a pair of smart eyeglasses, a head mounted display, or avirtual reality headset), or a similar type of device.

The location management system 340 includes one or more devices capableof receiving, generating, storing, processing, providing, and/or routinginformation associated with a vehicle involved in a vehicle experienceand/or provisioning a vehicle experience, as described elsewhere herein.The location management system 340 may include a communication deviceand/or a computing device. For example, the location management system340 may include a server, such as an application server, a clientserver, a web server, a database server, a host server, a proxy server,a virtual server (e.g., executing on computing hardware), or a server ina cloud computing system. In some implementations, the locationmanagement system 340 includes computing hardware used in a cloudcomputing environment.

The provisioning device 350 includes one or more devices capable ofreceiving, generating, storing, processing, and/or providing informationassociated with provisioning a vehicle experience (e.g., by providingaccess to a vehicle and/or a key of the vehicle), as described elsewhereherein. The provisioning device 350 may include a communication deviceand/or a computing device. For example, the provisioning device 350 mayinclude a kiosk device and/or vending machine that is configured toprovide access to a physical vehicle key of a vehicle, or a similar typeof device.

The vehicle 360 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith provisioning a vehicle experience involving the vehicle 360, asdescribed elsewhere herein. The vehicle 360 may include a communicationdevice and/or a computing device. For example, the vehicle 360 may becapable, via the communication device and/or the computing device, ofbeing provisioned for a vehicle experience via a digital key, aparticular communication, and/or a particular instruction (e.g., fromthe vehicle experience system 310, the location management system 340,and/or the provisioning device 350), as described elsewhere herein.

The driver qualification source 370 includes one or more devices capableof receiving, generating, storing, processing, providing, and/or routinginformation associated with qualifying a driver for a vehicleexperience, as described elsewhere herein. The driver qualificationsource 370 may include a communication device and/or a computing device.For example, the driver qualification source 370 may include a server,such as an application server, a client server, a web server, a databaseserver, a host server, a proxy server, a virtual server (e.g., executingon computing hardware), or a server in a cloud computing system. In someimplementations, the driver qualification source 370 includes computinghardware used in a cloud computing environment.

The network 380 includes one or more wired and/or wireless networks. Forexample, the network 380 may include a wireless wide area network (e.g.,a cellular network or a public land mobile network), a local areanetwork (e.g., a wired local area network or a wireless local areanetwork (WLAN), such as a Wi-Fi network), a personal area network (e.g.,a Bluetooth network), a near-field communication network, a telephonenetwork, a private network, the Internet, and/or a combination of theseor other types of networks. The network 380 enables communication amongthe devices of environment 300.

The number and arrangement of devices and networks shown in FIG. 3 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 3 . Furthermore, two or more devices shown in FIG. 3 maybe implemented within a single device, or a single device shown in FIG.3 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 300 may perform one or more functions described as beingperformed by another set of devices of environment 300.

FIG. 4 is a diagram of example components of a device 400, which maycorrespond to the vehicle experience system 310, the user device 320,the agent device 330, the location management system 340, a provisioningdevice 350, a vehicle 360, and/or the driver qualification source 370.In some implementations, the vehicle experience system 310, the userdevice 320, the agent device 330, the location management system 340,the provisioning device 350, the vehicle 360, and/or the driverqualification source 370 may include one or more devices 400 and/or oneor more components of device 400. As shown in FIG. 4 , device 400 mayinclude a bus 410, a Processor 420, a memory 430, a storage component440, an input component 450, an output component 460, and acommunication component 470.

Bus 410 includes a component that enables wired and/or wirelesscommunication among the components of device 400. Processor 420 includesa central processing unit, a graphics processing unit, a microprocessor,a controller, a microcontroller, a digital signal processor, afield-programmable gate array, an application-specific integratedcircuit, and/or another type of processing component. Processor 420 isimplemented in hardware, firmware, or a combination of hardware andsoftware. In some implementations, Processor 420 includes one or moreprocessors capable of being programmed to perform a function. Memory 430includes a random access memory, a read only memory, and/or another typeof memory (e.g., a flash memory, a magnetic memory, and/or an opticalmemory).

Storage component 440 stores information and/or software related to theoperation of device 400. For example, storage component 440 may includea hard disk drive, a magnetic disk drive, an optical disk drive, a solidstate disk drive, a compact disc, a digital versatile disc, and/oranother type of non-transitory computer-readable medium. Input component450 enables device 400 to receive input, such as user input and/orsensed inputs. For example, input component 450 may include a touchscreen, a keyboard, a keypad, a mouse, a button, a microphone, a switch,a sensor, a global positioning system component, an accelerometer, agyroscope, and/or an actuator. Output component 460 enables device 400to provide output, such as via a display, a speaker, and/or one or morelight-emitting diodes. Communication component 470 enables device 400 tocommunicate with other devices, such as via a wired connection and/or awireless connection. For example, communication component 470 mayinclude a receiver, a transmitter, a transceiver, a modem, a networkinterface card, and/or an antenna.

Device 400 may perform one or more processes described herein. Forexample, a non-transitory computer-readable medium (e.g., memory 430and/or storage component 440) may store a set of instructions (e.g., oneor more instructions, code, software code, and/or program code) forexecution by Processor 420. Processor 420 may execute the set ofinstructions to perform one or more processes described herein. In someimplementations, execution of the set of instructions, by one or moreprocessors 420, causes the one or more processors 420 and/or the device400 to perform one or more processes described herein. In someimplementations, hardwired circuitry may be used instead of or incombination with the instructions to perform one or more processesdescribed herein. Thus, implementations described herein are not limitedto any specific combination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 4 are provided asan example. Device 400 may include additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 4 . Additionally, or alternatively, a set ofcomponents (e.g., one or more components) of device 400 may perform oneor more functions described as being performed by another set ofcomponents of device 400.

FIG. 5 is a flowchart of an example process 500 associated withprovisioning a vehicle experience according to an authentication of adriver for the vehicle experience. In some implementations, one or moreprocess blocks of FIG. 5 may be performed by a vehicle experience system(e.g., vehicle experience system 310). In some implementations, one ormore process blocks of FIG. 5 may be performed by another device or agroup of devices separate from or including the vehicle experiencesystem, such as a user device (e.g., the user device 320), an agentdevice (e.g., the agent device 330), a location management system (e.g.,the location management system 340), and/or a driver qualificationsource (e.g., the driver qualification source 370). Additionally, oralternatively, one or more process blocks of FIG. 5 may be performed byone or more components of device 400, such as Processor 420, memory 430,storage component 440, input component 450, output component 460, and/orcommunication component 470.

As shown in FIG. 5 , process 500 may include receiving, from a userdevice, a service request associated with the driver and a vehicle(block 510). In some implementations, the service request includesdriver information associated with the driver and vehicle informationassociated with the vehicle. As further shown in FIG. 5 , process 500may include obtaining, based on the driver information, qualificationinformation associated with the driver (block 520).

As further shown in FIG. 5 , process 500 may include providing, to theuser device and based on the qualification information indicating thatthe driver is qualified for the vehicle experience, a verification codethat is associated with the driver and the vehicle (block 530). Asfurther shown in FIG. 5 , process 500 may include identifying, based onthe vehicle information, a location management system that is associatedwith the vehicle (block 540). As further shown in FIG. 5 , process 500may include causing the location management system to provision thevehicle experience based on the verification code (block 550).

As further shown in FIG. 5 , process 500 may include receiving, from thelocation management system, an authentication request associated with ascan of the verification code (block 560). As further shown in FIG. 5 ,process 500 may include authenticating the driver for the vehicleexperience based on the authentication request including scan dataassociated with the verification code (block 570). As further shown inFIG. 5 , process 500 may include causing, based on authenticating thedriver for the vehicle experience, the location management system toenable the driver to access the vehicle (block 580).

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5 . Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise forms disclosed. Modifications may be made in light of the abovedisclosure or may be acquired from practice of the implementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Itwill be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Although particular combinations of features are recited in the claimsand/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set. As used herein, aphrase referring to “at least one of” a list of items refers to anycombination of those items, including single members. As an example, “atleast one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c,and a-b-c, as well as any combination with multiple of the same item.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, or a combination of related and unrelateditems), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A system for authenticating a driver associatedwith a vehicle experience, the system comprising: one or more memories;and one or more processors, coupled to the one or more memories,configured to: receive, from a user device, a service request associatedwith a vehicle; generate a digital vehicle key associated with thevehicle in accordance with a device characteristic associated with theuser device; provide, to the user device, the digital vehicle key;receive an authentication request associated with the digital vehiclekey; and enable access to the vehicle based at least in part on theauthentication request.
 2. The system of claim 1, wherein the digitalvehicle key is configured to wirelessly enable access to the vehicle viathe user device using an application of the user device.
 3. The systemof claim 1, wherein the digital vehicle key is provided to the userdevice based at least in part on obtaining qualification informationassociated with the driver.
 4. The system of claim 1, wherein theauthentication request is received from a location management system,wherein the location management system is identified based on beingmapped to a location of the vehicle in a vehicle inventory datastructure.
 5. The system of claim 1, wherein the one or more processorsare further configured to: monitor, via vehicle experience informationfrom the user device or the vehicle, the vehicle experience; andfacilitate operation of the vehicle for the vehicle experience based onthe vehicle experience information.
 6. The system of claim 1, whereinthe one or more processors are further configured to: monitor, viavehicle experience information from the user device or the vehicle, thevehicle experience; and store, in a record log, the vehicle experienceinformation.
 7. The system of claim 1, wherein the digital vehicle keyis generated based at least in part on vehicle experience informationcorresponding to the service request.
 8. The system of claim 7, whereinthe vehicle experience information identifies a time period for thevehicle experience, and wherein the digital vehicle key is configured toenable access to the vehicle only during the time period.
 9. The systemof claim 7, wherein the vehicle experience information identifies alocation associated with the vehicle experience, and wherein the digitalvehicle key is configured to enable access to the vehicle only in anarea that includes the location.
 10. The system of claim 7, furthercomprising: providing, to a location management system, a notificationto provision the vehicle for the vehicle experience during a time periodidentified in the vehicle experience information, wherein the digitalvehicle key is generated based on a confirmation that the locationmanagement system has provisioned the vehicle for the vehicleexperience.
 11. A non-transitory computer-readable medium storing a setof instructions, the set of instructions comprising: one or moreinstructions that, when executed by one or more processors of a device,cause the device to: receive a service request associated with avehicle; generate a digital vehicle key associated with the vehicle inaccordance with a device characteristic associated with a user device ora request characteristic associated with the service request; provide,to a user device, the digital vehicle key; receive an authenticationrequest associated with the digital vehicle key; and enable access tothe vehicle based at least in part on the authentication request. 12.The non-transitory computer-readable medium of claim 11, wherein thedigital vehicle key is generated further based on at least one of: adriver characteristic; or a vehicle characteristic.
 13. Thenon-transitory computer-readable medium of claim 11, wherein the digitalvehicle key corresponds to a wireless key that provides access to thevehicle.
 14. The non-transitory computer-readable medium of claim 11,wherein the digital vehicle key enables access to the vehicle for aparticular time period.
 15. The non-transitory computer-readable mediumof claim 11, further comprising: providing information associated withthe digital vehicle key that permits the vehicle to recognize the userdevice based at least in part on the user device providing the digitalvehicle key via a wireless communication.
 16. A method forauthenticating a driver for a vehicle experience, comprising: receiving,by a device and from a user device, a service request for a vehicleexperience; identifying, by the device, a vehicle for the vehicleexperience that is associated with vehicle information in the servicerequest; generating, by the device and based on vehicle experienceinformation in the service request, a digital vehicle key in accordancewith a device characteristic associated with the user device; andproviding, by the device and to the user device, the digital vehicle keyto permit the driver to access the vehicle via the user device.
 17. Themethod of claim 16, wherein the digital vehicle key is configured towirelessly enable access to the vehicle via the user device.
 18. Themethod of claim 16, wherein the vehicle experience informationidentifies a time period for the vehicle experience, wherein the digitalvehicle key is configured to enable access to the vehicle only duringthe time period.
 19. The method of claim 16, wherein the vehicleexperience information identifies a location associated with the vehicleexperience, wherein the digital vehicle key is configured to enableaccess to the vehicle only in an area that includes the location. 20.The method of claim 16, further comprising: providing, to a locationmanagement system, a notification to provision the vehicle for thevehicle experience during a time period corresponding to the vehicleexperience information, wherein the digital vehicle key is generatedbased at least in part on the vehicle being provisioned for the vehicleexperience.